Unit testy #7
Closed
Unit testy #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 9 commits
August 27, 2010 14:56
Tags on features are indented at 0. Other tags are indented at the same level as Scenario headers (one shiftwidth). This matches all the examples I have read. Comments above a feature are indented at 0. Comments after a blank line are indented at the same level as Scenario headers (one shiftwidth). All other comments preserve the indent of the line before them.
Tags on features are indented at 0. Other tags are indented at the same level as Scenario headers (one shiftwidth). This matches all the examples I have read. Comments above a feature are indented at 0. Comments after a blank line are indented at the same level as Scenario headers (one shiftwidth). All other comments preserve the indent of the line before them.
…ded tables example.
|
I can't get the specs to run. Perhaps I need an older RSpec? |
|
I'll look into it. |
|
So it was using RSpec 1.3 for some reason. Now it is on the latest stable RSpec. It requires gvim and pbcopy commands, currently, but perhaps it can be rejigged to eliminate some dependencies. mvim works just as well, if you symlink it or update the spec file. Running them once sometimes fails but subsequent runs seem more deterministic. It is a Good Enough (TM) set up to test what I wanted to test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Okay. Unit tests that use vim server and pass all my criteria. In fact I ran them with :bufdo on my entire repository of feature files at work and I'm happy with the results. Add more example feature files in the spec directory if you like. They could be more fine grained tests but they've sufficed.